home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000197_news@columbia.edu_Sun Nov 20 20:37:37 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA12233
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 20 Nov 1994 15:37:41 -0500
Received: by apakabar.cc.columbia.edu id AA11871
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 20 Nov 1994 15:37:39 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc,alt.winsock
Subject: Re: winsock/pkt dvr hack possible?
Date: 20 Nov 1994 20:37:37 GMT
Organization: Columbia University
Lines: 45
Message-Id: <3aoc2h$bit@apakabar.cc.columbia.edu>
References: <3a67j8$j39@Mercury.mcs.com> <3anvci$dut@relay.tor.hookup.net> <1994Nov20.105834.33349@cc.usu.edu> <p.waltenberg.1154.2ECFB2E0@irl.cri.nz>
Nntp-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:1142 alt.winsock:22443
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <p.waltenberg.1154.2ECFB2E0@irl.cri.nz>,
Peter Waltenberg <p.waltenberg@irl.cri.nz> wrote:
>-------
>> Jeff is correct. The top of a sockets API is a TCP stream channel of
>>bytes, not packets. "It could be done..." means creating a second TCP/IP
>>stack feeding from the streams channel and packaging it into TCP/IP over
>>Ethernet frames to be passed to the application. Not very desirable, nor
>>realistic.
>> Joe D.
>
>Actually acheiving the required functionality is pretty trivial, just run the
>winsock on top of a packet multiplexor on top of a packet driver instead.
>Using packet mux on top of the packet driver you can get packet drivers for
>DOS boxes plus a packet driver for Trumpet winsock. Pktmux can be found on
>biochemistry.cwru.edu. (and quite a few other sites).
>The system has to be configured at the bottom (DOS) level to use packet
>drivers, but thats possible with nearly all configurations.
>
>I'll admit that going from Winsock to packet driver is nightmarish, but
>actually acheiving whats wanted , which is KA9Q in a DOS box with Winsock
>running isn't. Thats basically how my system is configured now.
>
But this doesn't address the original need.
The original requirement was being able to run MS-DOS Kermit over a
WinSock interface when WinSock is active over a serial line connection
made with Windows for Workgroups.
In this circumstance, you don't have the packet multiplexor nor the
real packet driver for the mux to sit on.
In the setup you describe there is no need to interface a virtual packet
driver with the WinSock API because the DOS session can talk with the
real packet driver.
In any case, the desired functionality is not available nor is it worth
creating. The only thing that makes sense is a telnet redirector.
Jeffrey Altman * PO Box 220415 * Great Neck, NY * 11022-0415 * (516) 466-5495
"C-Kermit: available on more platforms than any other communications software."
"Kermit FTP: sending files whenever and wherever they are needed."
*NEW* OS/2 version 5A(190): ftp kermit.columbia.edu /kermit/archives/ckoker.zip